Move punctuation out of code spans, fix bad backticks (#39704)

Author: Josh-Cena

files/en-us/learn_web_development/core/structuring_content/basic_html_syntax/index.md

@@ -72,7 +72,7 @@ The element is the opening tag, followed by content, followed by the closing tag
 
 ### Active learning: creating your first HTML element
 
-Edit the line below in the "Editable code" area by wrapping it with the tags `<em>` and `</em>.` To _open the element_, put the opening tag `<em>` at the start of the line. To _close the element_, put the closing tag `</em>` at the end of the line. Doing this should give the line italic text formatting! See your changes update live in the _Output_ area.
+Edit the line below in the "Editable code" area by wrapping it with the tags `<em>` and `</em>`. To _open the element_, put the opening tag `<em>` at the start of the line. To _close the element_, put the closing tag `</em>` at the end of the line. Doing this should give the line italic text formatting! See your changes update live in the _Output_ area.
 
 If you make a mistake, you can clear your work using the _Reset_ button. If you get really stuck, press the _Show solution_ button to see the answer.
 

files/en-us/learn_web_development/extensions/server-side/django/development_environment/index.md

@@ -395,7 +395,7 @@ py -3 -m django --version
 >
 > In Windows _Python 3_ scripts are launched by prefixing the command with `py -3`, although this can vary depending on your specific installation.
 > Try omitting the `-3` modifier if you encounter any problems with commands.
-> In Linux/macOS, the command is `python3.`
+> In Linux/macOS, the command is `python3`.
 
 > [!WARNING]
 > The rest of this **module** uses the _Linux_ command for invoking Python 3 (`python3`). If you're working on _Windows_ replace this prefix with: `py -3`

files/en-us/learn_web_development/extensions/server-side/django/models/index.md

@@ -278,7 +278,7 @@ books_containing_genre = Book.objects.filter(genre__name__icontains='fiction')
 
 > [!NOTE]
 > You can use underscores (`__`) to navigate as many levels of relationships (`ForeignKey`/`ManyToManyField`) as you like.
-> For example, a `Book` that had different types, defined using a further "cover" relationship might have a parameter name: `type__cover__name__exact='hard'.`
+> For example, a `Book` that had different types, defined using a further "cover" relationship might have a parameter name: `type__cover__name__exact='hard'`.
 
 There is a lot more you can do with queries, including backwards searches from related models, chaining filters, returning a smaller set of values, etc. For more information, see [Making queries](https://docs.djangoproject.com/en/5.0/topics/db/queries/) (Django Docs).
 

files/en-us/learn_web_development/extensions/server-side/express_nodejs/skeleton_website/index.md

@@ -428,7 +428,7 @@ const app = require("../app");
 
 > [!NOTE]
 > Node.js 14 and later support ES6 `import` statements for importing JavaScript (ECMAScript) modules.
-> To use this feature you have to add `"type": "module",` to your Express **package.json** file, all the modules in your application have to use `import` rather than `require()`, and for _relative imports_ you must include the file extension (for more information see the [Node documentation](https://nodejs.org/api/esm.html#introduction)).
+> To use this feature you have to add `"type": "module"` to your Express **package.json** file, all the modules in your application have to use `import` rather than `require()`, and for _relative imports_ you must include the file extension (for more information see the [Node documentation](https://nodejs.org/api/esm.html#introduction)).
 > While there are benefits to using `import`, this tutorial uses `require()` in order to match [the Express documentation](https://expressjs.com/en/starter/hello-world.html).
 
 The remainder of the code in this file sets up a node HTTP server with `app` set to a specific port (defined in an environment variable or 3000 if the variable isn't defined), and starts listening and reporting server errors and connections. For now you don't really need to know anything else about the code (everything in this file is "boilerplate"), but feel free to review it if you're interested.

files/en-us/mdn/writing_guidelines/writing_style_guide/index.md

@@ -422,7 +422,7 @@ In the repository, we maintain several word lists, located at [`.vscode/dictiona
 
 These are our recommendations for using certain technical terms:
 
-- **HTML elements**: Use the term "element" to refer to HTML and XML elements, instead of "tag". In addition, the element should be wrapped in angle brackets "<>" and should be styled using backticks (\`). For example, using \<input\> inside backticks will style it as `<input>` as is expected.
+- **HTML elements**: Use the term "element" to refer to HTML and XML elements, instead of "tag". In addition, the element should be wrapped in angle brackets "<>" and should be styled using backticks (`` ` ``). For example, using \<input\> inside backticks will style it as `<input>` as is expected.
 
   - **Correct**: the `<span>` element
   - **Incorrect**: the span tag
@@ -632,7 +632,7 @@ To maintain consistency across MDN Web Docs, keep the following guidelines in mi
   - **Incorrect**: The [`revert-layer`](/en-US/docs/Web/CSS/revert-layer) keyword.
   - **Correct**: [HTML DOM API](/en-US/docs/Web/API/HTML_DOM_API)
   - **Incorrect**: The [HTML DOM API](/en-US/docs/Web/API/HTML_DOM_API)
-- As shown in the previous examples, add code formatting using backticks (\`) to keywords and literals in the link text, even though the formatting is not used in page and section titles. For example, for the page title "Array() constructor", the link text will be [`Array()` constructor](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Array).
+- As shown in the previous examples, add code formatting using backticks (`` ` ``) to keywords and literals in the link text, even though the formatting is not used in page and section titles. For example, for the page title "Array() constructor", the link text will be [`Array()` constructor](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Array).
 
 #### Descriptive text
 

files/en-us/mozilla/add-ons/webextensions/api/cookies/getall/index.md

@@ -42,8 +42,8 @@ let getting = browser.cookies.getAll(
       - : An `object` defining which [storage partitions](/en-US/docs/Mozilla/Add-ons/WebExtensions/API/cookies#storage_partitioning) to return cookies from:
 
         - If omitted, only cookies from unpartitioned storage are returned.
-        - If included without `topLevelSite', all cookies from partitioned and unpartitioned storage are returned.
-        - If included with the specified `topLevelSite', cookies from the specified partition storage are returned.
+        - If included without `topLevelSite`, all cookies from partitioned and unpartitioned storage are returned.
+        - If included with the specified `topLevelSite`, cookies from the specified partition storage are returned.
 
         This object contains:
 

files/en-us/mozilla/add-ons/webextensions/api/runtime/getcontexts/index.md

@@ -52,7 +52,7 @@ A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that
 - `documentId`
   - : `string`. UUID of the document associated with the context, or undefined if the context is not hosted in a document.
 - `documentOrigin`
-  - : string`. The origin of the document associated with the context or undefined if the context is not hosted in a document.
+  - : `string`. The origin of the document associated with the context or undefined if the context is not hosted in a document.
 - `documentUrl`
   - : `string`. The URL of the document associated with the context or undefined if the context is not hosted in a document.
 - `frameId`

files/en-us/mozilla/add-ons/webextensions/internationalization/index.md

@@ -228,7 +228,7 @@ In addition, you can use such substitutions to specify parts of the string that
 Locales can be specified using a language code, such as `fr` or `en` or qualified with a script and region code, such as `en-US` or `zh-Hans-CN`. When your extension asks the i18n system for a string, it selects a string using this algorithm:
 
 1. Return the string if there is a `messages.json` file for the user's set browser locale containing the string. For example, if the user has set their browser to `en-US` and the extension provides the `_locales/en_US/messages.json` file.
-2. Otherwise, if the browser locale is qualified with a script or region (e.g., `en-US` or `zh-Hans-CN`) and there is a `messages.json` file for the regionless version and failing that the scriptless version of that locale and that file contains the string, return it. For example, if the user has set their browser to `zh-Hans-CN` (and there is no `_locales/zh_Hans_CN/messages.json` file) the i18n system looks for a string in `zh-Hans`, and if that isn't available, `zh.`
+2. Otherwise, if the browser locale is qualified with a script or region (e.g., `en-US` or `zh-Hans-CN`) and there is a `messages.json` file for the regionless version and failing that the scriptless version of that locale and that file contains the string, return it. For example, if the user has set their browser to `zh-Hans-CN` (and there is no `_locales/zh_Hans_CN/messages.json` file) the i18n system looks for a string in `zh-Hans`, and if that isn't available, `zh`.
 3. Otherwise, if there is a `messages.json` file for the `default_locale` defined in the `manifest.json`, and it contains the string, return it.
 4. Otherwise return an empty string.
 

files/en-us/mozilla/add-ons/webextensions/work_with_contextual_identities/index.md

@@ -109,7 +109,7 @@ if (browser.contextualIdentities === undefined) {
 
 Firefox installs with the contextual identity feature turned off. It's turned on when an extension using the `contextualIdentities` API is installed. However, the user can turn the feature off using an option on the preferences page (about:preferences), hence the need for the check.
 
-The script now uses {{WebExtAPIRef("contextualIdentities.query.")}} to determine whether any contextual identities are defined in the browser. If there are none, a message is added to the popup and the script stops.
+The script now uses {{WebExtAPIRef("contextualIdentities.query")}} to determine whether any contextual identities are defined in the browser. If there are none, a message is added to the popup and the script stops.
 
 ```js
   browser.contextualIdentities.query({}).then((identities) => {

files/en-us/mozilla/firefox/releases/29/index.md

@@ -81,7 +81,7 @@ _See the [Mozilla Hacks blog post](https://hacks.mozilla.org/2014/02/css-source-
 - The deprecated `Window.pkcs11` property has been removed; it was returning `null` since Firefox 3.0.14. ([Firefox bug 964964](https://bugzil.la/964964))
 - The {{domxref("Node.cloneNode()")}} and {{domxref("Document.importNode()")}} methods take the Boolean `deep` argument. Until now, if omitted, these methods acted as if the value of `deep` was `true`. But this behavior has been changed as per the latest spec, and if omitted, the methods will act as if the value was `false`. ([Firefox bug 937461](https://bugzil.la/937461))
 - `Window._content` is no longer available to Web content ([Firefox bug 946564](https://bugzil.la/946564)).
-- {{domxref("HTMLAnchorElement/port", "URLUtils.port")}} behavior has been slightly changed: set to `''` will set it to the default port associated with the protocol, and `0` to `0.` ([Firefox bug 930450](https://bugzil.la/930450))
+- {{domxref("HTMLAnchorElement/port", "URLUtils.port")}} behavior has been slightly changed: set to `''` will set it to the default port associated with the protocol, and `0` to `0`. ([Firefox bug 930450](https://bugzil.la/930450))
 - {{domxref("Document.referrer")}} is now based on the incumbent script ([Firefox bug 887928](https://bugzil.la/887928)).
 - The [Gamepad API](/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API) is enabled by default ([Firefox bug 878828](https://bugzil.la/878828)).
 - The `CanvasRenderingContext2D.drawSystemFocusRing()` method got renamed to {{domxref("CanvasRenderingContext2D.drawFocusIfNeeded()")}} ([Firefox bug 959820](https://bugzil.la/959820)).

files/en-us/mozilla/firefox/releases/49/index.md

@@ -89,7 +89,7 @@ page-type: firefox-release-notes
 - Added the _experimental_ and _non-standard_ {{domxref("HTMLMediaElement.seekToNextFrame()")}} method, which allows seeking frame-by-frame through video content ([Firefox bug 1235301](https://bugzil.la/1235301)). While you're encouraged to experiment with this method to help us understand how useful it is, _do not use it in production code!_
 - The {{domxref("HTMLLabelElement.form")}} property now returns the form with which the label's control is associated, if there is a control (and if that control is associated with a form). Previously, labels were directly associated with forms using this property ([Firefox bug 1268852](https://bugzil.la/1268852)).
 - Support for the third parameter of {{domxref("EventTarget.addEventListener()")}}, either a {{jsxref("Boolean")}} or an `EventListenerOptions` has been added ([Firefox bug 1266164](https://bugzil.la/1266164) and [Firefox bug 1266066](https://bugzil.la/1266066)).
-- The audio volume related values for {{domxref("KeyboardEvent.key")}} have been renamed. `"VolumeDown"` is now `"AudioVolumeDown"`, `"VolumeUp"` is now `"AudioVolumeUp"`, and `"VolumeMute"` is now `"AudioVolumeMute".` This brings Firefox into alignment with the latest draft of the UI Events specification ([Firefox bug 1272578](https://bugzil.la/1272578)). See [Code values for keyboard events](/en-US/docs/Web/API/UI_Events/Keyboard_event_code_values) for a full list of available key codes.
+- The audio volume related values for {{domxref("KeyboardEvent.key")}} have been renamed. `"VolumeDown"` is now `"AudioVolumeDown"`, `"VolumeUp"` is now `"AudioVolumeUp"`, and `"VolumeMute"` is now `"AudioVolumeMute"`. This brings Firefox into alignment with the latest draft of the UI Events specification ([Firefox bug 1272578](https://bugzil.la/1272578)). See [Code values for keyboard events](/en-US/docs/Web/API/UI_Events/Keyboard_event_code_values) for a full list of available key codes.
 - The keys previously referred to as `"MozHomeScreen"`, `"MozCameraFocusAdjust"`, and `"MozPhoneCall"` now have official names in the UI Events specification: `"GoHome"`, `"CameraFocus"`, and `"Call"`. Firefox 49 has been updated to use the new names ([Firefox bug 1272599](https://bugzil.la/1272599)). See [Code values for keyboard events](/en-US/docs/Web/API/UI_Events/Keyboard_event_code_values) for a full list of available key codes.
 - The key values `"Separator"` and `"MediaSkip"` have been removed, as they were deprecated and unused ([Firefox bug 1232919](https://bugzil.la/1232919)).
 - Key values and the corresponding key codes `"Hyper"` and `"Super"` have been added to represent these legacy modifier keys ([Firefox bug 1232919](https://bugzil.la/1232919)).

files/en-us/mozilla/firefox/releases/8/updating_add-ons/index.md

@@ -52,7 +52,7 @@ Similarly, a new global, `ChromeWorker`, was introduced to support allowing Work
 
 ## Security changes
 
-Support for SSL 2.0 has been removed. This shouldn't affect any current add-ons. However, for reference, some very old code was removed, as well as support for the preferences `security.enable_ssl2` (which is false by default), and all preferences starting with `security.ssl2.`
+Support for SSL 2.0 has been removed. This shouldn't affect any current add-ons. However, for reference, some very old code was removed, as well as support for the preferences `security.enable_ssl2` (which is false by default), and all preferences starting with `security.ssl2`.
 
 ## See also
 

files/en-us/web/api/audiocontext/setsinkid/index.md

@@ -93,7 +93,7 @@ mediaDeviceBtn.addEventListener("click", async () => {
 We also provide the user with a dropdown menu to allow them to change the audio output device on the fly. To do this, we:
 
 1. Provide a button to populate the dropdown menu. We first invoke {{domxref("MediaDevices.getUserMedia()")}} to trigger the permissions prompt we need to allow device enumeration, then use {{domxref("MediaDevices.enumerateDevices()")}} to get all the available devices. We loop through the different devices and make each one available as an option in a {{htmlelement("select")}} element. We also create a "None" option for the case where you don't want to play your audio in any output.
-2. Add a {{domxref("HTMLElement/change_event", "change")}} event listener to the {{htmlelement("select")}} element to change the sink ID and therefore the audio output device when a new value is selected. If "None" is selected in the dropdown, we invoke `setSinkId()` with the `{ type : 'none' }` object parameter to select no audio device, otherwise we run it with the audio device ID contained in the `<select>` element `value` attribute` as the parameter.
+2. Add a {{domxref("HTMLElement/change_event", "change")}} event listener to the {{htmlelement("select")}} element to change the sink ID and therefore the audio output device when a new value is selected. If "None" is selected in the dropdown, we invoke `setSinkId()` with the `{ type : 'none' }` object parameter to select no audio device, otherwise we run it with the audio device ID contained in the `<select>` element `value` attribute as the parameter.
 
 The output device can be changed during audio playback, as well as before, or between plays.
 

files/en-us/web/api/cssmathinvert/index.md

@@ -7,7 +7,7 @@ browser-compat: api.CSSMathInvert
 
 {{APIRef("CSS Typed Object Model API")}}
 
-The **`CSSMathInvert`** interface of the [CSS Typed Object Model API](/en-US/docs/Web/API/CSS_Object_Model) represents a CSS {{CSSXref('calc','calc()')}} used as `calc(1 / <value>).` It inherits properties and methods from its parent {{domxref('CSSNumericValue')}}.
+The **`CSSMathInvert`** interface of the [CSS Typed Object Model API](/en-US/docs/Web/API/CSS_Object_Model) represents a CSS {{CSSXref('calc','calc()')}} used as `calc(1 / <value>)`. It inherits properties and methods from its parent {{domxref('CSSNumericValue')}}.
 
 {{InheritanceDiagram}}
 

files/en-us/web/api/cssprimitivevalue/setstringvalue/index.md

@@ -56,7 +56,7 @@ None ({{jsxref("undefined")}}).
 - `InvalidAccessError` {{domxref("DOMException")}}
   - : Thrown if the CSS value doesn't contain a string value
     or if the string value can't be converted into the specified unit.
-- `NoModificationAllowedError' {{domxref("DOMException")}}
+- `NoModificationAllowedError` {{domxref("DOMException")}}
   - : Thrown if the property is read-only.
 
 ## Specifications

files/en-us/web/api/document/prepend/index.md

@@ -42,7 +42,7 @@ None ({{jsxref("undefined")}}).
 ### Prepending a root element to a document
 
 If you try to prepend an element to an existing HTML document,
-it might throw a `HierarchyRequestError' {{domxref("DOMException")}} given a {{HTMLElement("html")}} element already exists.
+it might throw a `HierarchyRequestError` {{domxref("DOMException")}} given a {{HTMLElement("html")}} element already exists.
 
 ```js
 let html = document.createElement("html");

files/en-us/web/api/element/checkvisibility/index.md

@@ -173,7 +173,7 @@ function updateCSS() {
 The results are shown below.
 If you change the selection the results will be applied to the test element (blue outline) and the results of the `checkVisibility()` for each setting should be displayed.
 So for example, if you set the `opacity: 0` that test (only) should indicate `false`.
-However if you set `display: none` then all tests should return `false.
+However if you set `display: none` then all tests should return `false`.
 
 {{ EmbedLiveSample('Test checkVisibility() with varied CSS', "100%", "200" ) }}
 

files/en-us/web/api/element/computedstylemap/index.md

@@ -53,7 +53,7 @@ a {
 ```
 
 We add JavaScript to grab our link and return back a definition list of all the CSS
-property values using `computedStyleMap().`
+property values using `computedStyleMap()`.
 
 ```js
 // get the element

files/en-us/web/api/htmlcanvaselement/contextrestored_event/index.md

@@ -53,6 +53,6 @@ canvas.addEventListener(
 
 ## See also
 
-- [`HTMLCanvasElement: contextlost` event](/en-US/docs/Web/API/HTMLCanvasElement/contextlost_event)
+- [`HTMLCanvasElement`: `contextlost` event](/en-US/docs/Web/API/HTMLCanvasElement/contextlost_event)
 - [`CanvasRenderingContext2D.isContextLost()`](/en-US/docs/Web/API/CanvasRenderingContext2D/isContextLost)
-- [OffscreenCanvas: contextlost` event](/en-US/docs/Web/API/OffscreenCanvas/contextlost_event)
+- [`OffscreenCanvas`: `contextlost` event](/en-US/docs/Web/API/OffscreenCanvas/contextlost_event)

files/en-us/web/api/paymentresponse/retry/index.md

@@ -29,7 +29,7 @@ retry(errorFields)
   - : An object, with the following properties:
     - `error` {{optional_inline}}
       - : A general description of a payment error from which the user may attempt to recover by retrying the payment, possibly after correcting mistakes in the payment information. `error` can be provided all by itself to provide only a generic error message, or in concert with the other properties to serve as an overview while other properties' values guide the user to errors in specific fields in the payment form.
-    - `paymentMethod {{optional_inline}}
+    - `paymentMethod` {{optional_inline}}
       - : Any payment-method-specific errors which may have occurred. This object's contents will vary depending on the payment method used.
 
 ### Return value